Methods and systems for modifying disk images to provide network interface card teaming capabilities

ABSTRACT

A system for modifying a virtual disk to provide network interface card (NIC) teaming capabilities to a virtual disk. The system can include a virtual disk that has access to one or more NICs. In some instances, the NICs are included in a NIC team that is also available to the virtual disk. A teaming module executing on a computer can identify the NIC team and responsively obtain a media access control (MAC) address of the NIC team. In response to obtaining the NIC team MAC address, the teaming module can obtain a network boot MAC address that was used to PXE boot the virtual disk. The teaming module can then replace the NIC team MAC address of each NIC in the NIC team with the obtained network boot MAC address. The system then boots from the virtual disk that has the modified NIC team configuration.

RELATED APPLICATIONS

This U.S. Patent Application claims priority to U.S. Provisional PatentApplication Ser. No. 61/166,762, filed on Apr. 5, 2009, the disclosureof which is considered part of the disclosure of this application and isherein incorporated by reference in its entirety.

FIELD OF THE DISCLOSURE

This application relates generally to generating and delivering virtualhard disk images. More specifically, the application relates togenerating and delivering virtual hard disk images that have networkinterface card teaming capabilities.

BACKGROUND OF THE DISCLOSURE

Link aggregation is a technology that can be used to link togethermultiple network ports to create a level of redundancy within anetworked environment and to increase the speed by which information istransmitted and processed. In some instances, link aggregation can beused to load balance network traffic amongst multiple network interfacecards (NICs), and can provide a level of fault tolerance and redundancyshould one or more NICs fail. In most cases implementations of linkaggregation in a system may conform to the IEEE 802.1AX standard or theIEEE 802.3ad standard. Link aggregation can be accomplished by teamingNICs together using teaming software or some other software or hardwareconfiguration able to link together multiple NICs. Linking or trunkingtogether NICs can permit the creation of a NIC aggregation that cantransmit and receive data over a network at speeds much greater than thespeed at which any single network interface card within the aggregationcan transmit or receive data.

When creating a virtual hard disk for use in a network boot system, anetwork filter driver associated with a network stack may bind to eachof the physical network interface cards on a provisioning server. Ifmultiple network interface cards on the provisioning server have beentrunked or linked together via network interface card teaming software,the network interface card teaming software can create a single unifiedvirtual network interface card team to which the network filter driverwill bind. Teaming software creates a network interface card team byassociating each NIC team member's physical MAC address. Whenprovisioning the virtual hard disk to a client machine, issues arisebecause the MAC addresses of the NICs differ on different machines.Therefore, the NIC teaming software cannot establish a team during boottime and therefore fails to stream the virtual disk.

The issues posed by creating a virtual disk based in part on a physicaldisk employing a teaming module to link network interface cards may notbe overcome by using the physical network interface card details of theclient machine and presenting them to the streamed operating system.Such a solution likely will fail because the MAC addresses associatedwith the physical network interface cards will differ from the MACaddresses on different computing machines. This difference can confusethe network stack and hinder the network stack from operating bothefficiently and properly. NIC teaming may also be limited to a privateimage mode because the physical MAC addresses differ from machine tomachine. The differing MAC addresses make it difficult for the NICteaming software to re-create a NIC team during boot time since each NICteam identifies the underline physical NIC by MAC address. Thus, a needexists for a virtual disk creation and delivery method that permits thevirtual disk to retain its network interface card teaming capabilitieswithout hindering the virtual disk provisioning process.

SUMMARY OF THE DISCLOSURE

In its broadest interpretation, this disclosure describes systems andmethods for provisioning a virtual disk having network interface cardteaming capabilities. Linking network interface cards (NIC) togetherusing network interface card teaming software creates a NIC team whichis an aggregate of the linked NICs. This NIC team can be used in thesystem as a single NIC that transmits and receives network data atspeeds greater than a single network interface card within the team.Issues can arise when this NIC team is included in a virtual diskbecause that virtual disk can identify the NIC team as the boot networkinterface card that can be used to stream applications and content tothe virtual disk. In many instances, a NIC teaming software requirementcan be that the NIC MAC addresses stored in a registry, match the MACaddress of the NIC team. The problems posed by requiring that the NICsof a NIC team have the same MAC address of the NIC team can be overcomeby identifying virtual protocol binding information associated with aNIC team and using that information to identify all the NICs within ateam. This solution is employed by the methods and systems describedherein.

In one aspect, described herein is a method for modifying a virtual diskto provide network interface card (NIC) teaming capabilities. A teamingmodule executing on a computer can identify a NIC team available to avirtual disk. In response to identifying the NIC team, the teamingmodule can obtain a media access control (MAC) address of the NIC team.Responsive to obtaining the NIC team MAC address, the teaming module canobtain a network boot MAC address used to PXE boot the virtual disk. Theteaming module can then replace the NIC team MAC address of each NIC inthe NIC team with the obtained network boot MAC address. The virtualdisk is then booted to create the NIC team.

In some embodiments, the network boot MAC address can comprise a PXEboot MAC address of a NIC used to PXE boot the virtual disk.

In other embodiments identifying the NIC team can further includeenumerating each NIC that is included in the NIC team.

Identifying the NIC team, in other embodiments, can include identifyinga NIC team that is configured to bind to a network stack filter driver.In some instances, identifying a NIC team bound to a network stackfilter driver can include parsing a registry of the virtual disk for asubkey specifying a bind to the network stack filter driver. In otherinstances, the NICs of the NIC team can be enumerated by parsing theregistry for NICs that have a global identifier substantially similar toa global identifier of the NIC team. In still other embodiments, the NICteam MAC address can be bound to the network stack filter driver.

In one embodiment, booting the virtual disk to create the NIC team caninclude updating a registry of the virtual disk to include the networkboot MAC address.

In some instances, described herein is a system for modifying a virtualdisk to provide network interface card (NIC) teaming capabilities. Thesystem can include a virtual disk, and a NIC team that is available tothe virtual disk and that includes a multiple NICs. A NIC teaming moduleexecuting on a computer can identify the NIC team and obtain, responsiveto identifying the NIC team, a media access control (MAC) address of theNIC team. The teaming module can obtain responsive to obtaining the NICteam MAC address, a network boot MAC address used to PXE boot thevirtual disk, and replace the NIC team MAC address of each NIC in theNIC team with the obtained network boot MAC address. The system thenboots from the virtual disk that has the modified NIC teamconfiguration.

BRIEF DESCRIPTION OF THE DRAWINGS

The following figures depict certain illustrative embodiments of a themethods and systems described herein, where like reference numeralsrefer to like elements. Each depicted embodiment is illustrative of themethod and system and not limiting.

FIG. 1A is a block diagram illustrative of an embodiment of aremote-access, networked environment with a client machine thatcommunicates with a server.

FIGS. 1B and 1C are block diagrams illustrative of an embodiment ofcomputing machines for practicing the methods and systems describedherein.

FIG. 2A is a block diagram illustrative of an embodiment of a physicalmachine.

FIG. 2B is a block diagram illustrative of an embodiment of a physicalmachine employing network interface card teaming.

FIG. 3 is a flow diagram illustrative of an embodiment of a method foroverriding the MAC address associated with a network interface cardteam.

DETAILED DESCRIPTION

FIG. 1A illustrates one embodiment of a computing environment 101 thatincludes one or more client machines 102A-102N (generally referred toherein as “client machine(s) 102”) in communication with one or moreservers 106A-106N (generally referred to herein as “server(s) 106”).Installed in between the client machine(s) 102 and server(s) 106 is anetwork.

In one embodiment, the computing environment 101 can include anappliance installed between the server(s) 106 and client machine(s) 102.This appliance can mange client/server connections, and in some casescan load balance client connections amongst a plurality of backendservers.

The client machine(s) 102 can in some embodiment be referred to as asingle client machine 102 or a single group of client machines 102,while server(s) 106 may be referred to as a single server 106 or asingle group of servers 106. In one embodiment a single client machine102 communicates with more than one server 106, while in anotherembodiment a single server 106 communicates with more than one clientmachine 102. In yet another embodiment, a single client machine 102communicates with a single server 106.

A client machine 102 can, in some embodiments, be referenced by any oneof the following terms: client machine(s) 102; client(s); clientcomputer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); endpoint node(s);or a second machine. The server 106, in some embodiments, may bereferenced by any one of the following terms: server(s), local machine;remote machine; server farm(s), host computing device(s), or a firstmachine(s).

In one embodiment, the client machine 102 can be a virtual machine 102C.The virtual machine 102C can be any virtual machine, while in someembodiments the virtual machine 102C can be any virtual machine managedby a hypervisor developed by XenSolutions, Citrix Systems, IBM, VMware,or any other hypervisor. In other embodiments, the virtual machine 102Ccan be managed by any hypervisor, while in still other embodiments, thevirtual machine 102C can be managed by a hypervisor executing on aserver 106 or a hypervisor executing on a client 102.

The client machine 102 can in some embodiments execute, operate orotherwise provide an application that can be any one of the following:software; a program; executable instructions; a virtual machine; ahypervisor; a web browser; a web-based client; a client-serverapplication; a thin-client computing client; an ActiveX control; a Javaapplet; software related to voice over internet protocol (VoIP)communications like a soft IP telephone; an application for streamingvideo and/or audio; an application for facilitating real-time-datacommunications; a HTTP client; a FTP client; an Oscar client; a Telnetclient; or any other set of executable instructions. Still otherembodiments include a client device 102 that displays application outputgenerated by an application remotely executing on a server 106 or otherremotely located machine. In these embodiments, the client device 102can display the application output in an application window, a browser,or other output window. In one embodiment, the application is a desktop,while in other embodiments the application is an application thatgenerates a desktop.

The server 106, in some embodiments, executes a remote presentationclient or other client or program that uses a thin-client orremote-display protocol to capture display output generated by anapplication executing on a server 106 and transmits the applicationdisplay output to a remote client 102. The thin-client or remote-displayprotocol can be any one of the following protocols: the IndependentComputing Architecture (ICA) protocol manufactured by Citrix Systems,Inc. of Ft. Lauderdale, Fla.; or the Remote Desktop Protocol (RDP)manufactured by the Microsoft Corporation of Redmond, Wash.

The computing environment 101 can include more than one server 106A-106Nsuch that the servers 106A-106N are logically grouped together into aserver farm 106. The server farm 106 can include servers 106 that aregeographically dispersed and logically grouped together in a server farm106, or servers 106 that are located proximate to each other andlogically grouped together in a server farm 106. Geographicallydispersed servers 106A-106N within a server farm 106 can, in someembodiments, communicate using a WAN, MAN, or LAN, where differentgeographic regions can be characterized as: different continents;different regions of a continent; different countries; different states;different cities; different campuses; different rooms; or anycombination of the preceding geographical locations. In some embodimentsthe server farm 106 may be administered as a single entity, while inother embodiments the server farm 106 can include multiple server farms106.

In some embodiments, a server farm 106 can include servers 106 thatexecute a substantially similar type of operating system platform (e.g.,WINDOWS NT, manufactured by Microsoft Corp. of Redmond, Wash., UNIX,LINUX, or SNOW LEOPARD.) In other embodiments, the server farm 106 caninclude a first group of servers 106 that execute a first type ofoperating system platform, and a second group of servers 106 thatexecute a second type of operating system platform. The server farm 106,in other embodiments, can include servers 106 that execute differenttypes of operating system platforms.

The server 106, in some embodiments, can be any server type. In otherembodiments, the server 106 can be any of the following server types: afile server; an application server; a web server; a proxy server; anappliance; a network appliance; a gateway; an application gateway; agateway server; a virtualization server; a deployment server; a SSL VPNserver; a firewall; a web server; an application server or as a masterapplication server; a server 106 executing an active directory; or aserver 106 executing an application acceleration program that providesfirewall functionality, application functionality, or load balancingfunctionality. In some embodiments, a server 106 may be a RADIUS serverthat includes a remote authentication dial-in user service. Inembodiments where the server 106 comprises an appliance, the server 106can be an appliance manufactured by any one of the followingmanufacturers: the Citrix Application Networking Group; Silver PeakSystems, Inc; Riverbed Technology, Inc.; F5 Networks, Inc.; or JuniperNetworks, Inc. Some embodiments include a first server 106A thatreceives requests from a client machine 102, forwards the request to asecond server 106B, and responds to the request generated by the clientmachine 102 with a response from the second server 106B. The firstserver 106A can acquire an enumeration of applications available to theclient machine 102 and well as address information associated with anapplication server 106 hosting an application identified within theenumeration of applications. The first server 106A can then present aresponse to the client's request using a web interface, and communicatedirectly with the client 102 to provide the client 102 with access to anidentified application.

The server 106 can, in some embodiments, execute any one of thefollowing applications: a thin-client application using a thin-clientprotocol to transmit application display data to a client; a remotedisplay presentation application; any portion of the CITRIX ACCESS SUITEby Citrix Systems, Inc. like the METAFRAME or CITRIX PRESENTATIONSERVER; MICROSOFT WINDOWS Terminal Services manufactured by theMicrosoft Corporation; or an ICA client, developed by Citrix Systems,Inc. Another embodiment includes a server 106 that is an applicationserver such as: an email server that provides email services such asMICROSOFT EXCHANGE manufactured by the Microsoft Corporation; a web orInternet server; a desktop sharing server; a collaboration server; orany other type of application server. Still other embodiments include aserver 106 that executes any one of the following types of hostedservers applications: GOTOMEETING provided by Citrix Online Division,Inc.; WEBEX provided by WebEx, Inc. of Santa Clara, Calif.; or MicrosoftOffice LIVE MEETING provided by Microsoft Corporation.

Client machines 102 can, in some embodiments, be a client node thatseeks access to resources provided by a server 106. In otherembodiments, the server 106 may provide clients 102 or client nodes withaccess to hosted resources. The server 106, in some embodiments,functions as a master node such that it communicates with one or moreclients 102 or servers 106. In some embodiments, the master node canidentify and provide address information associated with a server 106hosting a requested application, to one or more clients 102 or servers106. In still other embodiments, the master node can be a server farm106, a client 102, a cluster of client nodes 102, or an appliance.

One or more clients 102 and/or one or more servers 106 can transmit dataover a network 104 installed between machines and appliances within thecomputing environment 101. The network 104 can comprise one or moresub-networks, and can be installed between any combination of theclients 102, servers 106, computing machines and appliances includedwithin the computing environment 101. In some embodiments, the network104 can be: a local-area network (LAN); a metropolitan area network(MAN); a wide area network (WAN); a primary network 104 comprised ofmultiple sub-networks 104 located between the client machines 102 andthe servers 106; a primary public network 104 with a private sub-network104; a primary private network 104 with a public sub-network 104; or aprimary private network 104 with a private sub-network 104. Stillfurther embodiments include a network 104 that can be any of thefollowing network types: a point to point network; a broadcast network;a telecommunications network; a data communication network; a computernetwork; an ATM (Asynchronous Transfer Mode) network; a SONET(Synchronous Optical Network) network; a SDH (Synchronous DigitalHierarchy) network; a wireless network; a wireline network; or a network104 that includes a wireless link where the wireless link can be aninfrared channel or satellite band. The network topology of the network104 can differ within different embodiments, possible network topologiesinclude: a bus network topology; a star network topology; a ring networktopology; a repeater-based network topology; or a tiered-star networktopology. Additional embodiments may include a network 104 of mobiletelephone networks that use a protocol to communicate among mobiledevices, where the protocol can be any one of the following: AMPS; TDMA;CDMA; GSM; GPRS UMTS; or any other protocol able to transmit data amongmobile devices.

Illustrated in FIG. 1B is an embodiment of a computing device 100, wherethe client machine 102 and server 106 illustrated in FIG. 1A can bedeployed as and/or executed on any embodiment of the computing device100 illustrated and described herein. Included within the computingdevice 100 is a system bus 150 that communicates with the followingcomponents: a central processing unit 121; a main memory 122; storagememory 128; an input/output (I/O) controller 123; display devices124A-124N; an installation device 116; and a network interface 118. Inone embodiment, the storage memory 128 includes: an operating system,software routines, and a client agent 120. The I/O controller 123, insome embodiments, is further connected to a key board 126, and apointing device 127. Other embodiments may include an I/O controller 123connected to more than one input/output device 130A-130N.

FIG. 1C illustrates one embodiment of a computing device 100, where theclient machine 102 and server 106 illustrated in FIG. 1A can be deployedas and/or executed on any embodiment of the computing device 100illustrated and described herein. Included within the computing device100 is a system bus 150 that communicates with the following components:a bridge 170, and a first I/O device 130A. In another embodiment, thebridge 170 is in further communication with the main central processingunit 121, where the central processing unit 121 can further communicatewith a second I/O device 130B, a main memory 122, and a cache memory140. Included within the central processing unit 121, are I/O ports, amemory port 103, and a main processor.

Embodiments of the computing machine 100 can include a centralprocessing unit 121 characterized by any one of the following componentconfigurations: logic circuits that respond to and process instructionsfetched from the main memory unit 122; a microprocessor unit, such as:those manufactured by Intel Corporation; those manufactured by MotorolaCorporation; those manufactured by Transmeta Corporation of Santa Clara,Calif.; the RS/6000 processor such as those manufactured byInternational Business Machines; a processor such as those manufacturedby Advanced Micro Devices; or any other combination of logic circuits.Still other embodiments of the central processing unit 122 may includeany combination of the following: a microprocessor, a microcontroller, acentral processing unit with a single processing core, a centralprocessing unit with two processing cores, or a central processing unitwith more than one processing core.

While FIG. 1C illustrates a computing device 100 that includes a singlecentral processing unit 121, in some embodiments the computing device100 can include one or more processing units 121. In these embodiments,the computing device 100 may store and execute firmware or otherexecutable instructions that, when executed, direct the one or moreprocessing units 121 to simultaneously execute instructions or tosimultaneously execute instructions on a single piece of data. In otherembodiments, the computing device 100 may store and execute firmware orother executable instructions that, when executed, direct the one ormore processing units to each execute a section of a group ofinstructions. For example, each processing unit 121 may be instructed toexecute a portion of a program or a particular module within a program.

In some embodiments, the processing unit 121 can include one or moreprocessing cores. For example, the processing unit 121 may have twocores, four cores, eight cores, etc. In one embodiment, the processingunit 121 may comprise one or more parallel processing cores. Theprocessing cores of the processing unit 121, may in some embodimentsaccess available memory as a global address space, or in otherembodiments, memory within the computing device 100 can be segmented andassigned to a particular core within the processing unit 121. In oneembodiment, the one or more processing cores or processors in thecomputing device 100 can each access local memory. In still anotherembodiment, memory within the computing device 100 can be shared amongstone or more processors or processing cores, while other memory can beaccessed by particular processors or subsets of processors. Inembodiments where the computing device 100 includes more than oneprocessing unit, the multiple processing units can be included in asingle integrated circuit (IC). These multiple processors, in someembodiments, can be linked together by an internal high speed bus, whichmay be referred to as an element interconnect bus.

In embodiments where the computing device 100 includes one or moreprocessing units 121, or a processing unit 121 including one or moreprocessing cores, the processors can execute a single instructionsimultaneously on multiple pieces of data (SIMD), or in otherembodiments can execute multiple instructions simultaneously on multiplepieces of data (MIMD). In some embodiments, the computing device 100 caninclude any number of SIMD and MIMD processors.

The computing device 100, in some embodiments, can include a graphicsprocessor or a graphics processing unit (Not Shown). The graphicsprocessing unit can include any combination of software and hardware,and can further input graphics data and graphics instructions, render agraphic from the inputted data and instructions, and output the renderedgraphic. In some embodiments, the graphics processing unit can beincluded within the processing unit 121. In other embodiments, thecomputing device 100 can include one or more processing units 121, whereat least one processing unit 121 is dedicated to processing andrendering graphics.

One embodiment of the computing machine 100 includes a centralprocessing unit 121 that communicates with cache memory 140 via asecondary bus also known as a backside bus, while another embodiment ofthe computing machine 100 includes a central processing unit 121 thatcommunicates with cache memory via the system bus 150. The local systembus 150 can, in some embodiments, also be used by the central processingunit to communicate with more than one type of I/O device 130A-130N. Insome embodiments, the local system bus 150 can be any one of thefollowing types of buses: a VESA VL bus; an ISA bus; an EISA bus; aMicroChannel Architecture (MCA) bus; a PCI bus; a PCI-X bus; aPCI-Express bus; or a NuBus. Other embodiments of the computing machine100 include an I/O device 130A-130N that is a video display 124 thatcommunicates with the central processing unit 121. Still other versionsof the computing machine 100 include a processor 121 connected to an I/Odevice 130A-130N via any one of the following connections:HyperTransport, Rapid I/O, or InfiniBand. Further embodiments of thecomputing machine 100 include a processor 121 that communicates with oneI/O device 130A using a local interconnect bus and a second I/O device130B using a direct connection.

The computing device 100, in some embodiments, includes a main memoryunit 122 and cache memory 140. The cache memory 140 can be any memorytype, and in some embodiments can be any one of the following types ofmemory: SRAM; BSRAM; or EDRAM. Other embodiments include cache memory140 and a main memory unit 122 that can be any one of the followingtypes of memory: Static random access memory (SRAM), Burst SRAM orSynchBurst SRAM (BSRAM); Dynamic random access memory (DRAM); Fast PageMode DRAM (FPM DRAM); Enhanced DRAM (EDRAM), Extended Data Output RAM(EDO RAM); Extended Data Output DRAM (EDO DRAM); Burst Extended DataOutput DRAM (BEDO DRAM); Enhanced DRAM (EDRAM); synchronous DRAM(SDRAM); JEDEC SRAM; PC100 SDRAM; Double Data Rate SDRAM (DDR SDRAM);Enhanced SDRAM (ESDRAM); SyncLink DRAM (SLDRAM); Direct Rambus DRAM(DRDRAM); Ferroelectric RAM (FRAM); or any other type of memory. Furtherembodiments include a central processing unit 121 that can access themain memory 122 via: a system bus 150; a memory port 103; or any otherconnection, bus or port that allows the processor 121 to access memory122.

One embodiment of the computing device 100 provides support for any oneof the following installation devices 116: a CD-ROM drive, a CD-R/RWdrive, a DVD-ROM drive, tape drives of various formats, USB device, abootable medium, a bootable CD, a bootable CD for GNU/Linux distributionsuch as KNOPPIX®, a hard-drive or any other device suitable forinstalling applications or software. Applications can in someembodiments include a client agent 120, or any portion of a client agent120. The computing device 100 may further include a storage device 128that can be either one or more hard disk drives, or one or moreredundant arrays of independent disks; where the storage device isconfigured to store an operating system, software, programsapplications, or at least a portion of the client agent 120. A furtherembodiment of the computing device 100 includes an installation device116 that is used as the storage device 128.

The computing device 100 may further include a network interface 118 tointerface to a Local Area Network (LAN), Wide Area Network (WAN) or theInternet through a variety of connections including, but not limited to,standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56 kb,X.25, SNA, DECNET), broadband connections (e.g., ISDN, Frame Relay, ATM,Gigabit Ethernet, Ethernet-over-SONET), wireless connections, or somecombination of any or all of the above. Connections can also beestablished using a variety of communication protocols (e.g., TCP/IP,IPX, SPX, NetBIOS, Ethernet, ARCNET, SONET, SDH, Fiber Distributed DataInterface (FDDI), RS232, RS485, IEEE 802.11, IEEE 802.11a, IEEE 802.11b,IEEE 802.11g, CDMA, GSM, WiMax and direct asynchronous connections). Oneversion of the computing device 100 includes a network interface 118able to communicate with additional computing devices 100′ via any typeand/or form of gateway or tunneling protocol such as Secure Socket Layer(SSL) or Transport Layer Security (TLS), or the Citrix Gateway Protocolmanufactured by Citrix Systems, Inc. Versions of the network interface118 can comprise any one of: a built-in network adapter; a networkinterface card; a PCMCIA network card; a card bus network adapter; awireless network adapter; a USB network adapter; a modem; or any otherdevice suitable for interfacing the computing device 100 to a networkcapable of communicating and performing the methods and systemsdescribed herein.

Embodiments of the computing device 100 include any one of the followingI/O devices 130A-130N: a keyboard 126; a pointing device 127; mice;trackpads; an optical pen; trackballs; microphones; drawing tablets;video displays; speakers; inkjet printers; laser printers; anddye-sublimation printers; or any other input/output device able toperform the methods and systems described herein. An I/O controller 123may in some embodiments connect to multiple I/O devices 103A-130N tocontrol the one or more I/O devices. Some embodiments of the I/O devices130A-130N may be configured to provide storage or an installation medium116, while others may provide a universal serial bus (USB) interface forreceiving USB storage devices such as the USB Flash Drive line ofdevices manufactured by Twintech Industry, Inc. Still other embodimentsinclude an I/O device 130 that may be a bridge between the system bus150 and an external communication bus, such as: a USB bus; an AppleDesktop Bus; an RS-232 serial connection; a SCSI bus; a FireWire bus; aFireWire 800 bus; an Ethernet bus; an AppleTalk bus; a Gigabit Ethernetbus; an Asynchronous Transfer Mode bus; a HIPPI bus; a Super HIPPI bus;a SerialPlus bus; a SCI/LAMP bus; a FibreChannel bus; or a SerialAttached small computer system interface bus.

In some embodiments, the computing machine 100 can connect to multipledisplay devices 124A-124N, in other embodiments the computing device 100can connect to a single display device 124, while in still otherembodiments the computing device 100 connects to display devices124A-124N that are the same type or form of display, or to displaydevices that are different types or forms. Embodiments of the displaydevices 124A-124N can be supported and enabled by the following: one ormultiple I/O devices 130A-130N; the I/O controller 123; a combination ofI/O device(s) 130A-130N and the I/O controller 123; any combination ofhardware and software able to support a display device 124A-124N; anytype and/or form of video adapter, video card, driver, and/or library tointerface, communicate, connect or otherwise use the display devices124A-124N. The computing device 100 may in some embodiments beconfigured to use one or multiple display devices 124A-124N, theseconfigurations include: having multiple connectors to interface tomultiple display devices 124A-124N; having multiple video adapters, witheach video adapter connected to one or more of the display devices124A-124N; having an operating system configured to support multipledisplays 124A-124N; using circuits and software included within thecomputing device 100 to connect to and use multiple display devices124A-124N; and executing software on the main computing device 100 andmultiple secondary computing devices to enable the main computing device100 to use a secondary computing device's display as a display device124A-124N for the main computing device 100. Still other embodiments ofthe computing device 100 may include multiple display devices 124A-124Nprovided by multiple secondary computing devices and connected to themain computing device 100 via a network.

In some embodiments, the computing machine 100 can execute any operatingsystem, while in other embodiments the computing machine 100 can executeany of the following operating systems: versions of the MICROSOFTWINDOWS operating systems such as WINDOWS 3.x; WINDOWS 95; WINDOWS 98;WINDOWS 2000; WINDOWS NT 3.51; WINDOWS NT 4.0; WINDOWS CE; WINDOWS XP;and WINDOWS VISTA; the different releases of the Unix and Linuxoperating systems; any version of the MAC OS manufactured by AppleComputer; OS/2, manufactured by International Business Machines; anyembedded operating system; any real-time operating system; any opensource operating system; any proprietary operating system; any operatingsystems for mobile computing devices; or any other operating system. Instill another embodiment, the computing machine 100 can execute multipleoperating systems. For example, the computing machine 100 can executePARALLELS or another virtualization platform that can execute or managea virtual machine executing a first operating system, while thecomputing machine 100 executes a second operating system different fromthe first operating system.

The computing machine 100 can be embodied in any one of the followingcomputing devices: a computing workstation; a desktop computer; a laptopor notebook computer; a server; a handheld computer; a mobile telephone;a portable telecommunication device; a media playing device; a gamingsystem; a mobile computing device; a netbook; a device of the IPODfamily of devices manufactured by Apple Computer; any one of thePLAYSTATION family of devices manufactured by the Sony Corporation; anyone of the Nintendo family of devices manufactured by Nintendo Co; anyone of the XBOX family of devices manufactured by the MicrosoftCorporation; or any other type and/or form of computing,telecommunications or media device that is capable of communication andthat has sufficient processor power and memory capacity to perform themethods and systems described herein. In other embodiments the computingmachine 100 can be a mobile device such as any one of the followingmobile devices: a JAVA-enabled cellular telephone or personal digitalassistant (PDA), such as the i55sr, i58sr, i85s, i88s, i90c, i95c1, orthe im1100, all of which are manufactured by Motorola Corp; the 6035 orthe 7135, manufactured by Kyocera; the i300 or i330, manufactured bySamsung Electronics Co., Ltd; the TREO 180, 270, 600, 650, 680, 700p,700w, or 750 smart phone manufactured by Palm, Inc; any computing devicethat has different processors, operating systems, and input devicesconsistent with the device; or any other mobile computing device capableof performing the methods and systems described herein. In still otherembodiments, the computing device 100 can be any one of the followingmobile computing devices: any one series of Blackberry, or otherhandheld device manufactured by Research In Motion Limited; the iPhonemanufactured by Apple Computer; Palm Pre; a Pocket PC; a Pocket PCPhone; or any other handheld mobile device.

Illustrated in FIG. 2 is block diagram that illustrates an embodiment ofa physical machine 302 environment configured to provision a virtualdisk, but not configured to provision a virtual disk having networkinterface card (NIC) teaming capabilities. The physical machine 302includes a set of communication protocols such as the TCP/IP protocols314 or the IPX/SPX protocols 316 that can be used to transmit data overa network. The physical machine further includes two NICS, NIC 1 310 andNIC 2 312. Also included in the physical machine 302 a network driverinterface specification (NDIS) wrapper 304 in communication with anetwork stack filter driver 306, a first NIC driver 320, a second NICdriver 326, a first miniport driver instance 322 and a second miniportdriver instance 328. The network filter driver (BNNS) 306 is further incommunication with a protocol driver (BNIStack) 308.

Further referring to FIG. 2, and in more detail, the physical machine302 is a computing machine having the ability to perform logic orfunctions in accordance with programmed instructions. In someembodiments, the physical machine 302 may be a computing workstation, adesktop computer, a laptop or notebook computer, a server, or any of theother embodiments of the computing machine 100 listed above. Stillfurther embodiments include a physical machine 302 that is referred toby any of the following identifying labels: computing machine; computer;local computing machine; remote computing machine; first computingmachine; second computing machine; third computing machine; machine; orany other identifier used to denote some type of system having aprocessor and a memory element, wherein the processor is able to executesoftware commands. The physical machine 302 may be a physical computingmachine or virtual computing machine, and may have a characteristic orcharacteristics identifying the computing machine as one of either of aphysical machine or virtual machine.

A local physical disk (not shown) can be, in some embodiments, includedin the physical machine 302 and can be a hard disk drive. In furtherembodiments, the local physical disk may be a combination of physical orvirtual disks in a Redundant Array of Independent Disks (RAID). In oneembodiment, the local physical disk is in direct communication with anyone of the following machine components: an installer program (notshown), and the network driver interface specification (NDIS) wrapper304. In another embodiment, the local physical disk (not shown)communicates with the following machine components: a first NIC driver320, a second NIC driver 326, a first miniport driver instance 322 and asecond miniport driver instance 328. While in some embodiments a localphysical disk can be included, in other embodiments a virtual disk canbe included.

In communication with the NDIS wrapper 304 is a network filter driver(BNNS) 306 that intercepts network packets and determines if the networkpackets should be de-multiplexed to the NDIS wrapper 304 or BNIStack308. In one embodiment the BNNS 306 can determine a packet's destinationby examining the packet's header, and determining whether the socketsmatch. The BNNS 306 is an intermediate driver for the NDIS wrapper 304in that it can bind to third-party NICs and provide some networkservices. BNNS 306 is in communication with the BNIStack 308 which isthe protocol driver for computing machines. The BNIStack 308 can sendand receive messages from the filter driver (BNNS) 306 that filters allread/write requests issued to a virtual disk on either a client or aserver. When the read/write requests are issued to a virtual disk, therequests are filtered and sent to the protocol driver 308.

Further in communication with the NDIS wrapper 304 is a grouping ofelements related to the first NIC 310 and the second NIC 312 including aNIC driver 320, 326 and a miniport driver instance 322, 328. The firstand second NIC drivers 320, 326 are drivers used by the operating systemor the NDIS wrapper 304 to communicate with the first and second NICs310, 312. In some embodiments, the NIC drivers 320, 326 can be devicedrivers that provide an abstraction layer between the physical NICs 310,312 and the operating system. The first and second miniport driverinstances 322, 328 can facilitate communication between the operatingsystem and operating system components and other class drivers such asthe NIC drivers 320, 326. In one embodiment, the first and secondminiport driver instances 322, 328 are drivers that provide support fora specific network interface card present in a physical machine bytranslating inputs and outputs from the physical NIC into a format thatthe operating system can read and interact with, and may enable acomputing machine to communicate over a network with a second computingmachine (not illustrated). In one embodiment, each of the NIC drivers320, 326; and the miniport driver instances 322, 328 are used by thecomputing machine to communicate with the NICs 310, 312 and to furthercommunication over a network with remote computing machines.

In one embodiment, a NDIS wrapper 304 is included in the physicalmachine 302. The NDIS wrapper 304, in some embodiments, is a set ofexport libraries that provide both an abstraction layer and portabilityfor all interactions between a NIC or NIC miniport driver and theoperating system. When a program instructs the physical machine 302 tobind to a miniport driver 322, 328, the NDIS wrapper 304 may generatethe resultant binding information which can be stored within theoperating system, and included within the created virtual disk. In oneembodiment, the physical machine 302 may contain, in lieu of the NDISwrapper 304, an application, function, routine, logic, virtual object,or other set of code instructions having substantially equivalentfunctionality to that of the NDIS wrapper 304.

Further included in the physical machine 302 is a first and second NIC310, 312. In some embodiments, the NICs 310, 312 can be the same type ofNIC, while in other embodiments, the NICs 310, 312 can be differenttypes of NICs. The NIC can be referred to as a network adapter, anetwork interface controller, a LAN adapter or any other monikerindicating that the NIC is a hardware component within the physicalmachine 302 that permits the physical machine 302 to communicate over anetwork with other machines. In many embodiments, the NICs 310, 312 useMAC addresses, or unique serial numbers assigned to each NIC, to providelow level addressing at the physical network layer. While FIG. 2Aillustrates two NICs 310, 312, in other embodiments, any number of NICscan be included in the physical machine 302.

In one embodiment, the system described in FIG. 2A can include a NICteaming intermediate driver that can be used to implement a NIC team.The NIC teaming intermediate driver, in some embodiments, can be any NICteaming driver. In other embodiments, the NIC teaming intermediatedriver can be a NIC teaming driver manufactured by INTEL, INTEL ADVANCEDNETWORKING SERVICES, or BROADCOM, BROADCOM ADVANCED SERVER PROGRAM. TheNIC teaming driver can balance inbound and outbound network trafficamongst one or more NICs. In one embodiment, the NIC teaming driver canact as a single virtual protocol driver, and can enumerate a singlevirtual miniport interface that the upper NDIS wrapper 304 cancommunicate with. Thus, the NIC teaming driver can act as a singledriver for all NICs included in the system. Further, the NIC teamingdriver can handle load balancing and fault tolerance for the networktraffic handled by each NIC in the NIC team.

In some embodiments, the BNNS filter driver 306 can interface with theNIC teaming driver to take advantage of the functionality provided bythe NIC teaming driver. Embodiments where the BNNS filter driver 306positions itself on top of a NIC teaming driver may include: a NICminiport driver that can load at boot time (Start=0); a NIC intermediatedriver that can load at boot time (Start=0); and a target device thatcan be installed after NIC teaming is properly installed and configured.In the above-mentioned embodiment, the NIC teaming driver may onlyexpose one teamed NIC network interface through software basedmultiplexing or hardware based 802.3ad link aggregation for the upperlayer application (BNNS) 306. Applications such as operating systemstreaming and remote application delivery applications (e.g. XENAPP,XENDESKTOP) traffic can benefit from NIC teaming. Further, the virtualdisk or the target computer onto which the virtual disk is installed,may take advantage of the NIC teaming, the NIC hardware and softwarerich functionality. The remote application delivery application may alsobenefit from NIC teaming since it only needs to communicate with thesingle IP address.

Illustrated in FIG. 2B is an embodiment of the system illustrated inFIG. 2A that further includes a teaming module 362 that can facilitatechanging the configuration of the members of the NIC team. Also includedin this embodiment of the physical machine are the elements of NICteaming software that can be used to create the single aggregate NIC 364representative of the NIC team, these elements include: a MUX miniportdriver 350 in communication with a NIC teaming intermediate driver 352which is further in communication with a first MUX protocol instance 354and a second MUX protocol instance 356. All other aspects of thephysical machine 302, as described in FIG. 2A, are included.

The teaming module 362 can be any program, set of commands or softwareelement executable by a processor on the physical machine 302 to alterthe NIC teaming software 364 and further alter the configuration of theNIC team created by the NIC teaming software. In one embodiment, theteaming module 362 can carry out the method 402 illustrated in FIG. 3.In another embodiment, the teaming module 362 can carry out any numberof steps needed to alter the MAC addresses of the members of a NIC teamso that they all have a team MAC address corresponding to the MACaddress of a NIC used to PXE boot a streamed virtual hard disk. In someembodiments, the teaming module 362 may execute on the physical machine302 while in other embodiments, the teaming module 362 may execute on aremote computing machine in communication with the physical machine 302.

A third party or proprietary teaming software 364 can be used to createa NIC team. This NIC teaming software 364 can in some embodiments beused to generate the driver components of a single aggregate NIC 364representative of the NIC team. In one embodiment, the teaming software364 can include a multiplexed miniport driver 350 that comprises the NICteam's virtual miniport binding information, the NIC teamingintermediate driver 352 and the first and second multiplexed (MUX)protocol instances 354, 356. In one embodiment, the first and second MUXprotocol instances 354, 356 correspond to the members of the NIC teamwhich in this embodiment is the first and second NIC 310, 312. Thenumber of MUX protocol instances 354, 356 can in some embodimentscorrespond to the number of NICs included in the team. The physicalmachine 302 uses the NIC teaming software 364 components as the driversused to communicate with the members of the NIC team, i.e. the first andsecond NICS 310, 312, and to communicate over a network with remotecomputing machines. In some embodiments, the NIC teaming software 364can load balance the transmission and receipt of network packets amongstthe members of the NIC team. Load balancing using the NIC teamingsoftware 364 can increase the speed at which network packets aretransmitted and received over the network. In other embodiments, the NICteaming software 364 can be used to introduce NIC redundancy by issuingtransmit/receive commands to a second NIC team member when a first NICteam member fails. The teaming software 364 can in some embodimentsgenerate the NIC team with a NIC team virtual MAC address or networkaddress.

While FIGS. 2A and 2B illustrate embodiments of a system that utilizesNIC teaming, in some embodiments the systems can be employed on avirtual disk. Thus, the components illustrated as executing on thephysical machine 302 can execute on a virtual disk. In some embodiments,the virtual disk can be deployed on a virtual machine, while in otherembodiments the virtual disk can be deployed on a physical machine 302.In some embodiments, substantially each one of the components, with theexception of the physical NICs 310, 312 can be deployed on a virtualdisk. In other embodiments, substantially each one of the componentswith the exception of the physical NICs 310, 312 and the teaming module362 can be deployed on a virtual disk.

Illustrated in FIG. 3 is an embodiment of a method 402 for aiding theNIC teaming software 364 in altering the configuration of the NIC teamto further create a virtual disk that can have NIC teaming capabilitiesonce it is streamed to a remote machine. The method 402 includes firstidentifying the NIC team (Step 404) and then enumerating all of the NICswithin the registry (Step 406). Once all of the NICs are enumerated, adetermination must be made as to which NICs are within the NIC team(Step 408). The network address or the MAC address of the NIC that thevirtual disk uses to PXE boot is identified (Step 410). Once this PXEboot MAC address is identified, the MAC addresses or network addressesof each NIC that is a member of the NIC team is replaced with the PXEboot MAC address (Step 412). In some embodiments, all or portions of themethod 402 can be carried out by a teaming module executing on thephysical computer. In other embodiments, the teaming module can executeon another computer that is in communication with the physical computer.

Further referring to FIG. 3, and in more detail, the NIC team isidentified (Step 404) by identifying whether the upper bind of the NICteam points to the BNNS 306. The upper bind is a characteristic of a NICthat identifies where the NIC should pass packets once they arereceived. In embodiments where the NIC team's upper bind indicates thatnetwork packets should be passed up to the BNNS 306, that NIC team willbe identified as the NIC team of interest or the NIC team to be alteredby the teaming module 362. In some embodiments, the teaming module 362identifies the NIC team by searching through a registry or database toidentify the NIC team's virtual miniport binding information. In otherembodiments, the binding information and therefore the NIC team can beidentified by searching through a registry and iterating over subkeys ofHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E25-11CE-BFC1-08002BE10318}to determine which subkey has an upper bind that specified in BNNS.Determining that the upper bind specifies BNNS is by finding a subkeywhere <XXXX>\Linkage\UpperBind=BNNS. In some embodiments, determiningthe NIC team includes determining confirmation information associatedwith the third party NIC team. In one embodiment, the following isrecorded by the teaming module 362,<XXXX>\Linkage\Export=\Device\{guid}.

In some embodiments, identifying the NIC team can further includeidentifying or obtaining the PXE MAC address of the NIC team. This PXEMAC address can be bound to the BNNS 306. Determining the PXE MACaddress of the NIC team can include searching through the registry ofthe virtual disk to identify a key related to a NIC team and bound tothe BNNS network filter 306. Obtaining the NIC team MAC address can, insome embodiments, occur in response to identifying the NIC team.

Once the NIC team has been identified, all of the NICs are enumerated(Step 406) by enumerating all NICs and each by searching through theregistry for NICs have a global identifier or guid similar to the onestored by the teaming module 362. In one embodiment enumerating all theNICs includes enumerating all the NICs on a physical machine 302. Inother embodiments, enumerating all the NICs includes enumerating all theNICs included in the NIC team. Enumerating the NICs in the NIC team caninclude parsing the registry for NICs that have a global identifiersubstantially the same as the global identifier of the NIC team.

The teaming module 362 then identifies which NICs are members of the NICteam (Step 408) by determining which of the enumerated NICs have anupper bind specifying BNNS. In some embodiments determining whether anenumerated NIC has an upper bind specifying BNNS includes determiningwhether the MiniportBindingList subkey matches the LinkageExport of theidentified NIC team. The LinkageExport of the identified NIC team isequal to BNNS.

The teaming module 362 then identifies the network address or MACaddress used to PXE boot the virtual hard disk (Step 410), and replacesthe network address or MAC address associated with each member of theNIC team with the PXE boot MAC address (Step 412). This step, in someembodiments, can occur in response to obtaining the NIC team MACaddress. In other embodiments, the PXE boot MAC address can be a networkboot address that was used by the system to PXE boot the virtual disk.In one embodiment, the MAC addresses of each NIC within the NIC team arereplaced by searching through the subkeys ofHKEY_LOCAL_MACHINE\SYSTEM\CurrentControl|Set\Control\Class\{4D36E972-E25-11CE-BFC1-08002BE10318}and inserting the PXE boot MAC address in place of the NIC team virtualnetwork address stored in the registry keys for each NIC team member. Inother embodiments, the MAC address of the NIC third party teamingsoftware 364 is replaced with the PXE boot MAC address. Inserting thePXE boot MAC address in place of the virtual MAC address of the NICteam, permits the NIC teaming module included in the virtual disk toconfigure and recreate the team on a different machine. Once the virtualdisk image is corrected via the steps described in the method 402, thevirtual disk is streamed to a remote machine.

In some embodiments, replacing the NIC team settings with the PXE bootMAC address can include unbinding and uninstalling the PVS targetdevice. In these embodiments, the virtual disk may be required to beunbound and uninstalled, or the NIC team may be required to be unboundand uninstalled.

In other embodiments, the method can further include booting the systemfrom the virtual disk that has the modified NIC team configuration. Thismodified NIC team configuration can include the NIC team that has themodified NIC team MAC address. Booting the virtual disk to create theNIC team, in some embodiments, can include updating keys and subkeys ofa registry of the virtual disk to include the network boot MAC addressor PXE boot MAC address used to replace the NIC team MAC address.

The present disclosure may be provided as one or more computer-readableprograms embodied on or in one or more articles of manufacture. Thearticle of manufacture may be a floppy disk, a hard disk, a compactdisc, a digital versatile disc, a flash memory card, a PROM, a RAM, aROM, a computer readable medium having instructions executable by aprocessor, or a magnetic tape. In general, the computer-readableprograms may be implemented in any programming language. Some examplesof languages that can be used include C, C++, C#, or JAVA. The softwareprograms may be stored on or in one or more articles of manufacture asobject code.

While various embodiments of the methods and systems have beendescribed, these embodiments are exemplary and in no way limit the scopeof the described methods or systems. Those having skill in the relevantart can effect changes to form and details of the described methods andsystems without departing from the broadest scope of the describedmethods and systems. Thus, the scope of the methods and systemsdescribed herein should not be limited by any of the exemplaryembodiments and should be defined in accordance with the accompanyclaims and their equivalents.

1. A method for modifying a virtual disk to provide network interfacecard (NIC) teaming capabilities, the method comprising: identifying, bya teaming module executing on a computer, a NIC team available to avirtual disk; obtaining, by the teaming module responsive to identifyingthe NIC team, a media access control (MAC) address of the NIC team;obtaining, by the teaming module responsive to obtaining the NIC teamMAC address, a network boot MAC address used to PXE boot the virtualdisk; replacing, by the teaming module, the NIC team MAC address of eachNIC in the NIC team with the obtained network boot MAC address; andbooting the virtual disk to create the NIC team.
 2. The method of claim1, wherein obtaining the network boot MAC address further comprisesobtaining a PXE boot MAC address of a NIC used to PXE boot the virtualdisk.
 3. The method of claim 1, wherein identifying the NIC team furthercomprises enumerating each NIC included in the NIC team.
 4. The methodof claim 1, wherein identifying the NIC team further comprisesidentifying a NIC team bound to a network stack filter driver.
 5. Themethod of claim 4, wherein identifying a NIC team configured to bind tothe network stack filter driver further comprises parsing a registry ofthe virtual disk for a subkey specifying a bind to the network stackfilter driver.
 6. The method of claim 5, further comprising enumeratingthe NICs included in the NIC team by parsing the registry for NICshaving a global identifier substantially similar to a global identifierof the NIC team.
 7. The method of claim 4, wherein obtaining the NICteam MAC address further comprises obtaining a NIC team MAC addressbound to the network stack filter driver.
 8. The method of claim 1,wherein booting the virtual disk to create the NIC team furthercomprises updating a registry of the virtual disk to include the networkboot MAC address.
 9. A system for modifying a virtual disk to providenetwork interface card (NIC) teaming capabilities, the systemcomprising: a virtual disk; a NIC team available to the virtual disk,the NIC team comprising multiple NICs; and a teaming module executing ona computer to: identify the NIC team, obtain, responsive to identifyingthe NIC team, a media access control (MAC) address of the NIC team,obtain, responsive to obtaining the NIC team MAC address, a network bootMAC address used to PXE boot the virtual disk, and replace the NIC teamMAC address of each NIC in the NIC team with the obtained network bootMAC address.
 10. The system of claim 9, wherein the network boot MACaddress comprises a PXE boot MAC address of a NIC used to PXE boot thevirtual disk.
 11. The system of claim 9, wherein the teaming moduleidentifies the NIC team by enumerating each NIC included in the NICteam.
 12. The system of claim 9, wherein the teaming module identifiesthe NIC team by identifying a NIC team bound to a network stack filterdriver.
 13. The system of claim 12, wherein identifying a NIC teamconfigured to bind to the network stack filter driver further comprisesparsing a registry of the virtual disk for a subkey specifying a bind tothe network stack filter driver.
 14. The system of claim 13, furthercomprising enumerating the NICs included in the NIC team by parsing theregistry for NICs having a global identifier substantially similar to aglobal identifier of the NIC team.
 15. The system of claim 12, whereinthe NIC team MAC address is bound to the network stack filter driver.16. The system of claim 9, wherein the virtual disk updates a registryof the virtual disk to include the network boot MAC address.